Add parser errors to make sure we do not generate wrong bytecodes#70
Merged
smarr merged 1 commit intoSOM-st:masterfrom Jul 3, 2025
Merged
Conversation
…rictions Signed-off-by: Stefan Marr <git@stefan-marr.de>
smarr
force-pushed
the
add-check-that-arguments-fit-into-uint8_t
branch
from
c2539e9 to
68e80de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces
ParserError()calls to report when code goes over certain limits.For instance, we can currently only support 256 literal values, because the literal index is encoded as an 8bit number. The same restriction applies for field indexes etc.